Skip to content

Conversation

@hvdijk
Copy link
Collaborator

@hvdijk hvdijk commented Feb 18, 2025

Overview

Drop CA_RISCV_ENABLED CMake option.

Reason for change

The CA_RISCV_ENABLED option was provided because we simultaneously want to enable all available Mux targets by default, and disable the RISC-V Mux target by default. This is confusing when CA_RISCV_ENABLED and CA_MUX_TARGETS_TO_ENABLE are mismatched: it causes the RISC-V Mux target to be disabled when either variable disables it, even when the other variable suggests that it should be enabled.

Description of change

Drop CA_RISCV_ENABLED and rely entirely on CA_MUX_TARGETS_TO_ENABLE instead.

For consistency, make the same change to CA_MUX_COMPILERS_TO_ENABLE.

For both CA_MUX_TARGETS_TO_ENABLE and CA_MUX_COMPILERS_TO_ENABLE, change the default to "host": we expect builds that rely on other targets or other compilers to already explicitly specify the desired target and compiler.

Anything else we should know?

If there's any other relevant information we should know that may help us in
understanding and verifying your patch, please include it here.

Checklist

  • Read and follow the project Code of Conduct.
  • Make sure the project builds successfully with your changes.
  • Run relevant testing locally to avoid regressions.
  • Run clang-format-19 on all modified code.

@hvdijk hvdijk requested a review from a team as a code owner February 18, 2025 16:18
@hvdijk hvdijk force-pushed the drop-riscv-enabled branch 2 times, most recently from f04e99b to c2f792a Compare February 18, 2025 17:33
@hvdijk hvdijk force-pushed the drop-riscv-enabled branch 4 times, most recently from f3d0ce9 to d74316e Compare July 23, 2025 18:55
The CA_(target)_ENABLED options were provided because we simultaneously
wanted to enable all available Mux targets by default, and disable the
RISC-V Mux target by default. This is confusing when CA_RISCV_ENABLED and
CA_MUX_TARGETS_TO_ENABLE are mismatched: it causes the RISC-V Mux target
to be disabled when either variable disables it, even when the other
variable suggests that it should be enabled. Drop CA_(target)_ENABLED and
rely entirely on CA_MUX_TARGETS_TO_ENABLE instead.

For consistency, make the same change to CA_MUX_COMPILERS_TO_ENABLE.

For CA_MUX_TARGETS_TO_ENABLE, change the default to "host". For
CA_MUX_COMPILERS_TO_ENABLE, change the default to match
CA_MUX_TARGETS_TO_ENABLE. Update the documentation and continuous
integration to set them where we do not want host and were not already
setting them.
@hvdijk hvdijk force-pushed the drop-riscv-enabled branch from d74316e to 6b8255e Compare July 24, 2025 11:56
Copy link
Collaborator

@uwedolinsky uwedolinsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok to me.

@hvdijk hvdijk merged commit 17dc279 into uxlfoundation:main Jul 24, 2025
22 checks passed
@hvdijk hvdijk deleted the drop-riscv-enabled branch July 24, 2025 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants